[NTG-context] Re: Bug or feature? \numexpression and hashes

03. Thanks in advance. bug or feature: just something not done yet (there are probably a few more places) ... i added it (no upload) Hans - Hans Hagen | PRAGMA ADE Ridderstraat

[NTG-context] Bug or feature? \numexpression and hashes

Hi, list. The following fails with a "Missing number, treated as zero" error prompt: \starttext \expandedrepeat2{\expandedrepeat2{\the\numexpression#I+#P\relax\ }} \stoptext OTOH, \numexpr works seamlessly. Tested on ConTeXt 2023.09.03 19:03. Thanks in advance. Best regards, Jairo

[NTG-context] Re: (feature proposal) link to attachments: /GoToE

On 9/3/23 16:02, Henning Hraban Ramm wrote: > Am 03.09.23 um 13:03 schrieb Pablo Rodriguez: > [...] > While I don’t know what’s missing under the hood, I think there’s just a > “reference” key missing in \attachment or \setupattachment: Many thanks for your reply, Hraban. I’m afraid that

[NTG-context] Re: (feature proposal) link to attachments: /GoToE

Am 03.09.23 um 13:03 schrieb Pablo Rodriguez: On 9/3/23 12:46, Hans Hagen wrote: On 9/3/2023 12:17 PM, Pablo Rodriguez wrote: [...] This basic implementation of GoToE links would be extremely helpful to access embedded documents (believe it or not, this is something I explain almost every week

[NTG-context] Re: (feature proposal) link to attachments: /GoToE

On 9/3/23 12:46, Hans Hagen wrote: > On 9/3/2023 12:17 PM, Pablo Rodriguez wrote: >> [...] >> This basic implementation of GoToE links would be extremely helpful to >> access embedded documents (believe it or not, this is something I >> explain almost every week at work). >> >> I would be happy to

[NTG-context] Re: (feature proposal) link to attachments: /GoToE

On 9/3/2023 12:17 PM, Pablo Rodriguez wrote: Hi Hans, having attachments in PDF is very useful, but the vast majority of people don’t know how to handle them (even with the attachment pane displayed when Acrobat opens the document, or with file annotation). It would be really useful to have a

[NTG-context] (feature proposal) link to attachments: /GoToE

Hi Hans, having attachments in PDF is very useful, but the vast majority of people don’t know how to handle them (even with the attachment pane displayed when Acrobat opens the document, or with file annotation). It would be really useful to have a link with destination that it would open the

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

On 9/2/23 12:42, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 02.09.2023 um 12:35: >> [...] >> Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I >> know I should know better, but I‘m stuck at this): >> >> \definefontfamily[mainface][rm][DejaVu Sans] >>

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

Pablo Rodriguez schrieb am 02.09.2023 um 12:35: [...] Sorry, but I don‘t know why this doesn‘t get the slanted font as bold (I know I should know better, but I‘m stuck at this): \definefontfamily[mainface][rm][DejaVu Sans] [sl≃style:bf] You're using the wrong symbol (you have a math

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

On 9/2/23 12:18, Wolfgang Schuster wrote: > Hans Hagen schrieb am 02.09.2023 um 11:53: > [...] >> in lpdf-lmt.lmt you can try: >> >> l 593 >> >> tmsy = tmsy * sc >> >> l 610 >> >> tmsy = tmsy * f_y_scale > > I get now with LMTX the same output as I get with MkIV, the slant stays > the same for all

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

Hans Hagen schrieb am 02.09.2023 um 11:53: On 9/2/2023 11:45 AM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 02.09.2023 um 10:25: Dear list, I have the following sample (using current latest from 2023.08.27 13:48):    \setupinteractionscreen[option=max]   

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

On 9/2/2023 11:45 AM, Wolfgang Schuster wrote: Pablo Rodriguez schrieb am 02.09.2023 um 10:25: Dear list, I have the following sample (using current latest from 2023.08.27 13:48):    \setupinteractionscreen[option=max]    \definefontfamily[maf][rm][DejaVu Sans] [sl={style:tf,

[NTG-context] Re: slanted font feature: LMTX vs. MkIV

Pablo Rodriguez schrieb am 02.09.2023 um 10:25: Dear list, I have the following sample (using current latest from 2023.08.27 13:48): \setupinteractionscreen[option=max] \definefontfamily[maf][rm][DejaVu Sans] [sl={style:tf, features:{default,slanted}}] \setupbodyfont[maf, 8pt]

[NTG-context] slanted font feature: LMTX vs. MkIV

Dear list, I have the following sample (using current latest from 2023.08.27 13:48): \setupinteractionscreen[option=max] \definefontfamily[maf][rm][DejaVu Sans] [sl={style:tf, features:{default,slanted}}] \setupbodyfont[maf, 8pt] \setupfittingpage[offset=1ex] \starttext

[NTG-context] Fwd: Kerning feature not working

Forwarded Message Subject: Re: [NTG-context] Kerning feature not working Date: Wed, 30 Aug 2023 22:17:43 +0200 From: Hans Hagen To: Marcus Vinicius Mesquita On 8/30/2023 9:37 PM, Marcus Vinicius Mesquita wrote: Dear List In the MWE below, the kerning feature works OK

[NTG-context] Kerning feature not working

Dear List In the MWE below, the kerning feature works OK for ebgaramonditalic but not for ebgaramondregular. How do I fix it? I'm using ConTeXt version: 2023.08.27 13:48 \startluacode fonts.handlers.otf.addfeature { name = "kernit", type = "kern",

Re: [NTG-context] wider font effect as font feature?

On 1/20/2023 1:59 PM, Pablo Rodriguez via ntg-context wrote: Dear list, I wanted to use a font with slightly wider effect, such as in: \definetweakedfont[wider][xscale=1.075] Is there any way that it could be applied as a font feature? Or how could I apply this effect everytime

[NTG-context] wider font effect as font feature?

Dear list, I wanted to use a font with slightly wider effect, such as in: \definetweakedfont[wider][xscale=1.075] Is there any way that it could be applied as a font feature? Or how could I apply this effect everytime a \definefontfamily is used? Many thanks for your help, Pablo

Re: [NTG-context] issue with OT feature in LMTX

On 12/4/22 13:34, Hans Hagen via ntg-context wrote: > On 12/3/2022 2:04 PM, Pablo Rodriguez via ntg-context wrote: >> [...] >> Am I missing something or have I hit a bug in LMTX? > more a bug in your approach: you specify a range where you also > overwrite private slots (that happen to be used

Re: [NTG-context] issue with OT feature in LMTX

] \setupbodyfont[mainface] \definestructureconversionset [sectionnumbers] [0,n,Characters,g,n] [n] \definefontfeature[section] [smcp=yes, c2sc=yes] \setupheads[sectionconversionset=sectionnumbers] \setuphead[section][style={\feature[+][section

[NTG-context] issue with OT feature in LMTX

[sectionnumbers] [0,n,Characters,g,n] [n] \definefontfeature[section] [smcp=yes, c2sc=yes] \setupheads[sectionconversionset=sectionnumbers] \setuphead[section][style={\feature[+][section]}] \starttext \section{Just text} {\feature[+][section]Just text} \stoptext

Re: [NTG-context] LMTX: reimplementing texquotes as OTF feature

} Since `` and "' map to the same character, only "' works. The table has only 5 entries, not 6! (This took me a while to realize. ;)) > best not use an existign feature because we accumulate ... features > come in order (you can force order if needed as you probably saw in > one of the

Re: [NTG-context] LMTX: reimplementing texquotes as OTF feature

On 11/11/2022 10:19 PM, Leah Neukirchen via ntg-context wrote: Hi, as Hans recommended in the last video meeting, I tried to implement the texquotes feature using OTF features, and hit two problems: 1) To support German quotes as well, I have two ligatures that end up as the same glyph

[NTG-context] LMTX: reimplementing texquotes as OTF feature

Hi, as Hans recommended in the last video meeting, I tried to implement the texquotes feature using OTF features, and hit two problems: 1) To support German quotes as well, I have two ligatures that end up as the same glyph: `` -> “ "' -> “ This can't be in the sa

Re: [NTG-context] If a Font Has Ligature Glyphs But No Feature?

On 7/20/2022 9:40 PM, Bruce Horrocks via ntg-context wrote: On 20 Jul 2022, at 05:31, Michael Urban via ntg-context wrote: Aside from purchasing a real font product from Linotype at enormous expense and hoping it is better equipped, is there a way to coerce ConTeXt into using the

Re: [NTG-context] If a Font Has Ligature Glyphs But No Feature?

ve a lot of features in the first place I've so far >> not noticed any problems. I'm sure a real expert could tell you how to >> retain 'default' and add the ligatures, if needed. > > Hi Bruce, you can simply inherit your feature sets from default: > > \definefontfeature [venetian

Re: [NTG-context] If a Font Has Ligature Glyphs But No Feature?

the ligatures, if needed. Hi Bruce, you can simply inherit your feature sets from default: \definefontfeature [venetian-301-demi-ligatures][default][v1=yes,v3=yes] \definefontfeature [venetian-301-BT-ligatures][default][v2=yes,v3=yes] I’d like to borrow your example for my book, if you don’t object. Hraban

Re: [NTG-context] If a Font Has Ligature Glyphs But No Feature?

> On 20 Jul 2022, at 05:31, Michael Urban via ntg-context > wrote: > > Aside from purchasing a real font product from Linotype at enormous expense > and hoping it is better equipped, is there a way to coerce ConTeXt into using > the ligature glyphs for fi and fl? Yes - I had to do the same

Re: [NTG-context] If a Font Has Ligature Glyphs But No Feature?

On 7/20/2022 6:31 AM, Michael Urban via ntg-context wrote: I downloaded something that purports to be Century Expanded from fontsgeek.com. Although the font has fi and fl ligature glyphs, it does not have a ligature font feature and ConTeXt does not use those glyphs. Aside from purchasing

[NTG-context] If a Font Has Ligature Glyphs But No Feature?

I downloaded something that purports to be Century Expanded from fontsgeek.com. Although the font has fi and fl ligature glyphs, it does not have a ligature font feature and ConTeXt does not use those glyphs. Aside from purchasing a real font product from Linotype at enormous expense

[NTG-context] check whether font feature is being used

} {yes}{no}\\ \feature[+][asc] text \doifelsecurrentfonthasfeature{asc} {yes}{no} \doifelsefontfeature{asc} {yes}{no} \doifunknownfontfeature{asc} {yes}{no} \stopTEXpage \stoptext Sorry, but which is the right way to check when the font feature is being deployed? Many thanks

Re: [NTG-context] upload ... new feature

On 12/10/21 6:37 PM, Hans Hagen via ntg-context wrote: > On 12/10/2021 6:04 PM, Pablo Rodriguez via ntg-context wrote: >> [...] >> I’m afraid I’m not getting anything different. >> [...] >> I wonder whether there has been an LMTX update or something else that >> I’m missing (Linux64). > >

Re: [NTG-context] upload ... new feature

] [--permissions="see context --help --expert"] Many thanks for the new feature, Hans. I’m afraid I’m not getting anything different. Here is the source: \nopdfcompression \starttext \null \stoptext "context --purgeall --userpassword=foo a" outputs https://pdf.ousia.t

Re: [NTG-context] upload ... new feature

t --help --expert"] Many thanks for the new feature, Hans. I’m afraid I’m not getting anything different. Here is the source: \nopdfcompression \starttext \null \stoptext "context --purgeall --userpassword=foo a" outputs https://pdf.ousia.tk/enc.pdf. "context --purgeall

Re: [NTG-context] upload ... new feature

> On 10 Dec 2021, at 11:46, Hans Hagen via ntg-context > wrote: > > Hi, > > This time the lmtx upload has a (for some maybe) interesting new features: > runtime pdf encryption. > > > I would be surprised if the native apple viewer works but I can't test that. Apple Preview works without

[NTG-context] upload ... new feature

o" userpassword="" permissions="print,extract,quality" Now, this is a feature that relies on the viewer to deal properly with it as we only support the not depricated method (why bother with the old stuff). acrobat : it took some effort (and trial and error) to make

Re: [NTG-context] Synonyms feature request

On 11/12/2021 4:22 AM, Rik Kabel via ntg-context wrote: Hello developers, Is it possible to get a mechanism to reset and setup synonyms by way (page, part, chapter, section, ...)? This is not a high-priority request. I currently accomplish this in the after key of chapter setuphead

[NTG-context] Synonyms feature request

Hello developers, Is it possible to get a mechanism to reset and setup synonyms by way (page, part, chapter, section, ...)? This is not a high-priority request. I currently accomplish this in the after key of chapter setuphead definitions. However, it seems cleaner to define it when the

Re: [NTG-context] font feature

> On 8. Jul 2021, at 23:33, Hans Hagen wrote: > > you forgot the 'default' so you basically force basemode which is does > permanent features .. add/subtract works only in node mode > > \definefontfeature > [f:onum] > [onum=yes,pnum=yes] > > \definefontfamily [test] [serif]

Re: [NTG-context] font feature

On 7/8/2021 9:46 AM, Thomas A. Schmitz wrote: Hi all, is it possible to subtract a featureset that has been applied to a fontfamily? MWE: \definefontfeature   [f:frac]   [frac=yes,onum=no,pnum=no] \definefontfeature   [f:onum]   [onum=yes,pnum=yes] \definefontfamily [test] [serif]

[NTG-context] font feature

Hi all, is it possible to subtract a featureset that has been applied to a fontfamily? MWE: \definefontfeature [f:frac] [frac=yes,onum=no,pnum=no] \definefontfeature [f:onum] [onum=yes,pnum=yes] \definefontfamily [test] [serif] [AntykwaTorunska] [features=f:onum] \definefontfamily

Re: [NTG-context] tlig feature sometimes does not work

> work when the character is not in the font itself. Is that the case? > > Is this a bug or a feature? > > > > \starttext > > > > > \definefontfallback[fall][dejavusansmono][0-0xf][check=yes,force=no] > > \definefontsynonym[Test][file:Mikhak-Medium.ttf][f

Re: [NTG-context] tlig feature sometimes does not work

On 3/13/2021 2:01 AM, Mohammad Hossein Bateni wrote: Umm... the fallbacks are correct.  My conclusion is that tlig does not work when the character is not in the font itself.  Is that the case? Is this a bug or a feature? \starttext  \definefontfallback[fall][dejavusansmono][0-0xf

Re: [NTG-context] tlig feature sometimes does not work

On 3/13/2021 1:13 AM, Mohammad Hossein Bateni wrote: Any idea why the ligature {U+647 and U+654 => U+6C0} does not kick in? because it's not defined as ligature - Hans Hagen | PRAGMA ADE

Re: [NTG-context] tlig feature sometimes does not work

Umm... the fallbacks are correct. My conclusion is that tlig does not work when the character is not in the font itself. Is that the case? Is this a bug or a feature? \starttext \definefontfallback[fall][dejavusansmono][0-0xf][check=yes,force=no] \definefontsynonym[Test][file:Mikhak

Re: [NTG-context] tlig feature sometimes does not work

for this other Farsi font >> > ( >> https://github.com/aminabedi68/Mikhak/blob/master/Font/ttf/Mikhak-Medium.ttf >> > < >> https://github.com/aminabedi68/Mikhak/blob/master/Font/ttf/Mikhak-Medium.ttf>). >> >> > Perhaps this is because the last

Re: [NTG-context] tlig feature sometimes does not work

is is because the last font is not standard, but > > TrueType/OpenType standard is sometimes up for interpretation. > > > > I see two strange symptoms here: > > > > \showotfcomposition displays the tlig feature differently for the last > > font. It appears

Re: [NTG-context] tlig feature sometimes does not work

ype standard is sometimes up for interpretation. I see two strange symptoms here: \showotfcomposition displays the tlig feature differently for the last font.  It appears in the "extra" list, not in "basic".  Why is that? What does this mean anyway? The font doesn't have endas

[NTG-context] tlig feature sometimes does not work

this is because the last font is not standard, but TrueType/OpenType standard is sometimes up for interpretation. I see two strange symptoms here: \showotfcomposition displays the tlig feature differently for the last font. It appears in the "extra" list, not in "basic". Why is that?

[NTG-context] RE : Missing kern when using \feature

OK makes sense. I’ll see if I can remove this \feature macro.Yes 2nd case was only for reference for working case.Thanks De : Hans HagenEnvoyé le :vendredi 8 janvier 2021 16:32À : mailing list for ConTeXt users; JosephObjet :Re: [NTG-context] Missing kern when using \feature On 1/8/2021 2:45 PM

Re: [NTG-context] Missing kern when using \feature

][default][kern=yes] \definefontfamily[mainfont][serif][EBGaramond] \setupbodyfont[mainfont, 9pt] \showfontkerns \starttext Chapitre {\feature[-][xvicentury]v}. % no kerning between v and . indeed there should be no kerning because there are two different font setups (lmtx is a bit better

[NTG-context] Missing kern when using \feature

][serif][EBGaramond]\setupbodyfont[mainfont, 9pt]\showfontkerns \starttextChapitre {\feature[-][xvicentury]v}. % no kerning between v and . Chapitre v.\stoptext   ___ If your question is of interest to others as well

[NTG-context] Font feature not applied in some cases

I could reproduce this occasionally occuring unexpected output in following MWE.Seems linked to calt=yes feature being set and ordn=yes being set and letter ‘f’ (some other letters such as ‘b’ work fine). Thanks as always for help. \definefontfeature[noteref][mode=node, ordn=yes

[NTG-context] Questions concerning interfaces (and a feature request)

Hi, Hans and list. I want to know two things. 1. If the "option/content" pair could be enabled for hashes and arrays in interfaces.definecommand: \starttext \startluacode interfaces.definecommand{ name = "acommand", --This doesn't work --arguments = {"content", "array"}, arguments =

Re: [NTG-context] issue with defined font feature

On 12/26/20 6:36 PM, Wolfgang Schuster wrote: > Pablo Rodriguez schrieb am 26.12.2020 um 12:58: >> I have the following sample: >> [...] >> I’m not being able to get both lnum and no en-dashes: the defined font >> feature seems to require the default and I cannot get

Re: [NTG-context] issue with defined font feature

12123 -- 123\\ \tt 12123 -- 123 \stopTEXpage \stoptext I’m not being able to get both lnum and no en-dashes: the defined font feature seems to require the default and I cannot get en-dashes disabled when the default font feature set is enabled. You need "script=auto" (or a vali

[NTG-context] issue with defined font feature

able to get both lnum and no en-dashes: the defined font feature seems to require the default and I cannot get en-dashes disabled when the default font feature set is enabled. Does anyone what I am doing wrong here? Many thanks for your help, Pablo -- http://www.ousia.tk

[NTG-context] mkiv \digits{2.0=} zero padding feature request

Hi, As Wolfgang has figured out, zero padding in \digits only works for trailing (and omitted) zeroes when immediately preceded by the decimal separator. It would be nice if this would work even if there is a number preceding, so that \digits{3.1=}x\crlf \digits{3.==}x\crlf \digits{3.14}x

Re: [NTG-context] Disappearing font feature

the default setting for the font. The default for the italic faces is the single-storey form, so I need only apply the changed feature to the upright faces to get what I want. -- Rik ___ If your question

Re: [NTG-context] Disappearing font feature

while trying to reproduce the example, i ran into some confusion myself... I downloaded the fonts and installed them, then ran the script: mtxrun --generate mtxrun --script font --reload context --make verifying the existence of the font within the context region: mtxrun --script fonts --list

Re: [NTG-context] Disappearing font feature

On 12/22/2019 5:36 AM, Rik Kabel wrote: List, I have a strange case of a font feature disappearing when many fonts are used. In creating a sampler for the Jost* font (free at https://indestructibletype.com/Jost.html) and using its feature ss01 to get single-storey lower-case a, the font

[NTG-context] Disappearing font feature

List, I have a strange case of a font feature disappearing when many fonts are used. In creating a sampler for the Jost* font (free at https://indestructibletype.com/Jost.html) and using its feature ss01 to get single-storey lower-case a, the font reverts to the default two-storey a when

Re: [NTG-context] [feature] update

On 09-08-19 16:18, Hans Hagen wrote: > it uses rsync so it already does partial downloads > but it is still very verbose... is there a less-verbose switch ? .F pEpkey.asc Description: application/pgp-keys ___ If

Re: [NTG-context] [feature] update

On 8/9/2019 2:32 PM, Floris van Manen wrote: I do a daily update of the context distribution using the command sh ./first-setup.sh --modules=all --engine=luatex This works well, but is rather verbose on the screen. Would it be possible to have a less verbose version? Or that the script could

[NTG-context] [feature] update

I do a daily update of the context distribution using the command sh ./first-setup.sh --modules=all --engine=luatex This works well, but is rather verbose on the screen. Would it be possible to have a less verbose version? Or that the script could check some kind of a checksum before deciding to

Re: [NTG-context] feature request

Hi Alan, > 1) when new to Context, coming from LaTeX and learning a new system; ... > One gets over the first case rather quickly and then there is no > going back: the philosophies are so different. Hmm, I'll make an effort to be a LaTeX user and also ConTeXt user. Best regards, Atsuhito Kohda

Re: [NTG-context] feature request

Hi Aditya, > You can create a private module with the definitions that you need. If > these are general enough, then you can also release it as a third party > module for others to use. I don't see the value of adding (and > maintaining!) a module that provides LaTeX compatibility as part of the

Re: [NTG-context] feature request

opers (Alan, Aditya, and others) have contributed math > typesetting macros over time, but these follow the ConTeXt philosophy of > providing strong defaults but trying to avoid feature creep. Therefore > bmatrix, vmatrix, etc. are not defined by default, but as you saw from > my last mes

Re: [NTG-context] feature request

On Thu, 4 Jul 2019 11:16:22 -0400 (EDT) Aditya Mahajan wrote: > > BTW, I constantly convert Beamer documents into ConTeXt's > > simpleslide documents recently and it is very convenient > > if I can use \pmatrix{a\cr c\cr} style because it is similar > > to LaTeX documents. > > You can create

Re: [NTG-context] feature request

On Thu, 4 Jul 2019, Atsuhito Kohda wrote: Hi Henri, Thanks for your suggestions, they are very instructive. However, my request is not a smart way of displaying matrices but to know why \bmatrix and \vmatrix are not provided in core part of ConTeXt although \pmatrix is provided already in

Re: [NTG-context] feature request

and last I checked matrix algebra was not part of the curriculum. Other developers (Alan, Aditya, and others) have contributed math typesetting macros over time, but these follow the ConTeXt philosophy of providing strong defaults but trying to avoid feature creep. Therefore bmatrix, vmatrix, etc

Re: [NTG-context] feature request

Hi Henri, Thanks for your suggestions, they are very instructive. However, my request is not a smart way of displaying matrices but to know why \bmatrix and \vmatrix are not provided in core part of ConTeXt although \pmatrix is provided already in math-pln.mkiv About matrices, I first found

Re: [NTG-context] feature request

On 3/07/19 6:00 PM, Atsuhito Kohda wrote: > I've used LaTeX quite a long time but recently I begin to use ConTeXt too. > So I'm very sorry if the following is well-known issue. > > I find an example of \pmatrix in p.21 of "ConTeXt Mark IV an excursion" > (ma-cb-en.pdf). And I notice it is

Re: [NTG-context] feature request

On 3/07/19 6:00 PM, Atsuhito Kohda wrote: > I've used LaTeX quite a long time but recently I begin to use ConTeXt too. > So I'm very sorry if the following is well-known issue. > > I find an example of \pmatrix in p.21 of "ConTeXt Mark IV an excursion" > (ma-cb-en.pdf). And I notice it is

[NTG-context] feature request

I've used LaTeX quite a long time but recently I begin to use ConTeXt too. So I'm very sorry if the following is well-known issue. I find an example of \pmatrix in p.21 of "ConTeXt Mark IV an excursion" (ma-cb-en.pdf). And I notice it is defined in

Re: [NTG-context] Missing font features in page header if \feature[-] is used in header text

On 4/14/2019 6:20 PM, Joseph Canedo wrote: Dear list, With latest ConTeXt beta (13-04-2019) I notice that font features seem ignored in page header rendering. (missing kern between Ps in « Psalme » and different Th in « Thimothee ». Anything I am doing wrong ? fixed in next beta

[NTG-context] Missing font features in page header if \feature[-] is used in header text

. Thanks Best regards Joseph \definefontfeature[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes] \definefontfeature[xvicentury][] \definefontfamily[mainfont][serif][EBGaramond][features=base] \setupbodyfont[mainfont, 9pt] \showfontkerns \def\wrongheader{First book {\feature

Re: [NTG-context] open type feature "frac"

On 9/28/2018 10:56 PM, Ulrike Fischer wrote: Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature

[NTG-context] open type feature "frac"

Due to a question on tex.sx (https://tex.stackexchange.com/questions/452969/luatex-fontfeaturefractions-on-turns-first-digits-into-superscripts) I looked again (see https://www.mail-archive.com/ntg-context@ntg.nl/msg84822.html) at the frac feature. The output is still not really satisfactory

Re: [NTG-context] Missing font features in page header if \feature[-]is used in header text

Thanks a lot Hans for your prompt response. De : Hans Hagen Envoyé le :mercredi 30 mai 2018 16:17 À : mailing list for ConTeXt users; Joseph Canedo Objet :Re: [NTG-context] Missing font features in page header if \feature[-]is used in header text On 5/30/2018 2:31 PM, Joseph Canedo wrote

Re: [NTG-context] Missing font features in page header if \feature[-] is used in header text

[base][mode=node, liga=yes, dlig=yes, hlig=yes, kern=yes] \definefontfeature[xvicentury][] \definefontfamily[mainfont][serif][EBGaramond][features=base] \setupbodyfont[mainfont, 9pt] \showfontkerns \def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.} %% \feature[-] seems

[NTG-context] Missing font features in page header if \feature[-] is used in header text

, kern=yes] \definefontfeature[xvicentury][] \definefontfamily[mainfont][serif][EBGaramond][features=base] \setupbodyfont[mainfont, 9pt] \showfontkerns \def\wrongheader{First book {\feature[-][xvicentury]v} Psalme De David.} %% \feature[-] seems to cause problems in header \def\headerok{First book v

Re: [NTG-context] Feature request: \digits command

ups of three digits. Hi, Does this feature exist now in ConTeXt? TIA for any hints, -- Peter ___ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-co

Re: [NTG-context] (fake) bold as font feature

embold feature (similar to the slanted font feature) that fakes the bold font with \starteffect[both]...\stopeffect and it doesn’t strecht the font? much is possible if i can motivate myself Good to know in order to propose new features :-). Hm. Fake bold / slanted / small caps / of a bas

Re: [NTG-context] (fake) bold as font feature

On Mon, Mar 26, 2018 at 11:02 PM, Pablo Rodriguez <oi...@gmx.es> wrote: > On 03/26/2018 07:24 PM, Hans Hagen wrote: >> On 3/26/2018 4:55 PM, Hans Hagen wrote: >>> On 3/26/2018 1:40 PM, Pablo Rodriguez wrote: >>>> Hans, >>>> >>>> would it

Re: [NTG-context] (fake) bold as font feature

On 03/27/2018 09:01 AM, Hans Hagen wrote: > On 3/26/2018 11:02 PM, Pablo Rodriguez wrote: >> [...] >> Just out of curiosity (and not related to this feature), I see that >> Windows and Linux binaries (both 64bit) in the Suite contain different >> versions (1.08 v. 1

Re: [NTG-context] (fake) bold as font feature

On 3/26/2018 11:02 PM, Pablo Rodriguez wrote: On 03/26/2018 07:24 PM, Hans Hagen wrote: On 3/26/2018 4:55 PM, Hans Hagen wrote: On 3/26/2018 1:40 PM, Pablo Rodriguez wrote: Hans, would it be possible to add a embold feature (similar to the slanted font feature) that fakes the bold font

Re: [NTG-context] (fake) bold as font feature

On 03/26/2018 07:24 PM, Hans Hagen wrote: > On 3/26/2018 4:55 PM, Hans Hagen wrote: >> On 3/26/2018 1:40 PM, Pablo Rodriguez wrote: >>> Hans, >>> >>> would it be possible to add a embold feature (similar to the slanted >>> font feature) that f

Re: [NTG-context] (fake) bold as font feature

On 3/26/2018 4:55 PM, Hans Hagen wrote: On 3/26/2018 1:40 PM, Pablo Rodriguez wrote: Hans, would it be possible to add a embold feature (similar to the slanted font feature) that fakes the bold font with \starteffect[both]...\stopeffect and it doesn’t strecht the font? much is possible if i

Re: [NTG-context] (fake) bold as font feature

On 3/26/2018 1:40 PM, Pablo Rodriguez wrote: Hans, would it be possible to add a embold feature (similar to the slanted font feature) that fakes the bold font with \starteffect[both]...\stopeffect and it doesn’t strecht the font? much is possible if i can motivate myself This was already

[NTG-context] (fake) bold as font feature

Hans, would it be possible to add a embold feature (similar to the slanted font feature) that fakes the bold font with \starteffect[both]...\stopeffect and it doesn’t strecht the font? This was already requested by Ulrike Fischer (https://mailman.ntg.nl/pipermail/ntg-context/2017/090094.html

[NTG-context] understanding the \feature command

Dear list, I have the following sample: \definefontfeature [f:protrusion] [protrusion=quality] % \definefontfeature [f:noprotrusion] [protrusion=none] \setupalign[hanging] \starttext \feature[+][f:protrusion] \input knuth \blank[2*big] \feature[-][f:protrusion

Re: [NTG-context] Feature request: display Lua version

On Thu, Feb 22, 2018 at 11:39 AM, Procházka Lukáš Ing. wrote: > Hello, > > namely due to planned embedding Lua 5.3 into ConTeXt, would it be possible > ConTeXt to show Lua version being used? _VERSION is always available: $echo 'print(_VERSION)' > /tmp/test-v.lua $ luatex

Re: [NTG-context] Feature request: display Lua version

On 2/22/2018 11:39 AM, Procházka Lukáš Ing. wrote: Hello, namely due to planned embedding Lua 5.3 into ConTeXt, would it be possible ConTeXt to show Lua version being used? Something like: d:\Lukas\ConTeXt\Test>context.exe --version mtx-context | ConTeXt Process Management 1.02

[NTG-context] Feature request: display Lua version

Hello, namely due to planned embedding Lua 5.3 into ConTeXt, would it be possible ConTeXt to show Lua version being used? Something like: d:\Lukas\ConTeXt\Test>context.exe --version mtx-context | ConTeXt Process Management 1.02 mtx-context | mtx-context | main context file:

Re: [NTG-context] frac font feature doesn't work as expected

Am Wed, 5 Apr 2017 13:00:29 +0200 schrieb luigi scarso: > if you see > fonts > otf chain > feature 'frac', type > 'gsub_contextchain', chain lookup 's_s_7': is not yet supported (1) > then ... it need to be supported. Yes, that's what I see ;-(. -- Ul

Re: [NTG-context] frac font feature doesn't work as expected

1000/100 \usetypescriptfile[libertine] \setupbodyfont[libertine,12pt] \definefontfeature[frac][frac=yes] \starttext {\addff{frac} 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100} \stoptext if you see fonts > otf chain > feature 'frac', type 'gsub_contextchain', chain l

[NTG-context] frac font feature doesn't work as expected

\starttext \font\test={file:linlibertine_r.otf:+frac} \test 1/2 3/4 5/6 7/8 9/10 11/12 31415/27182 1000/100 \stoptext gives as output ½ 3¾ 5⅚ 7⅜ 9/10 1⅟12 31415/27182 1000/100 (I couldn't build an example without the primitive command. After \definefontfeature[frac][frac=yes]

[NTG-context] bug in \definefontfamily? (was: Re: OT salt feature not working?)

Gyre Pagella and the second line was Neo Euler. The default feature for the whole text was old numbers. TeX Gyre Pagella works fine with it, but Neo Euler (with \definefontfamily) doesn’t honour "onum". But \definefont works fine, so I guess something might be improved in \definefont

Re: [NTG-context] OT salt feature not working?

On 03/18/2017 11:05 PM, Pablo Rodriguez wrote: > Dear list, > > I have the following sample: > [...] > I get the same results with or without the first line commented out. > (I’m using latest beta from 2017.03.02 22:23.) > > Is this a bug or what am I missing? The issue is with the font:

  1   2   3   4   5   6   7   >